home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950329-19950528
/
000052_news@columbia.edu_Thu Apr 6 14:39:21 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA12657
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Thu, 6 Apr 1995 10:39:24 -0400
Received: by apakabar.cc.columbia.edu id AA08582
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Thu, 6 Apr 1995 10:39:23 -0400
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: "Can't open output file"
Date: 6 Apr 1995 14:39:21 GMT
Organization: Columbia University
Lines: 30
Message-Id: <3m0uep$8c4@apakabar.cc.columbia.edu>
References: <19950405.225622.346792.NETNEWS@uicvm.uic.edu>
Nntp-Posting-Host: watsun.cc.columbia.edu
Cc:
In article <19950405.225622.346792.NETNEWS@uicvm.uic.edu>,
Paul Clifford <pcliff@tigger.cc.uic.edu> wrote:
>When using linux kermit (local) and c-kermit (remote), I get the
>message "Can't open output file" when attempting to download a
>file to my local machine. I used to be able to download successfully,
>but now the transfer always aborts with the above message. I may have
>changed some settings, but can't figure out which.
>
This means that a file was coming in, Kermit got the name of the file
from the incoming file header packet, transformed the name (or not)
according to your SET FILE NAMES setting, got the attributes from the
attribute packet, and then tried to create a new file with the given name,
in either the current directory or, if you had SET RECEIVE PATHNAMES ON
and SET FILENAMES LITERAL, in whatever directory was included in the
incoming filename... and then failed for some reason. Normally the reason
is printed using perror(), like: write access denied, disk full, or something
like that.
To rule out all of the above, run Kermit with its default FILE NAMES and
RECEIVE PATHNAMES settings (namely, CONVERTED and OFF, respectively), and
make sure your current directory is writeable and your disk or partition is
not full.
If you still have a problem, then the next question would be: did you install
Kermit setuid or setgid? If so, did you follow the instructions carefully
for doing this?
If you still can't figure out what's wrong, email me directly.
- Frank <fdc@columbia.edu>